System for data storage and retrieval

ABSTRACT

A method for providing access to a database for product life cycle support (PLCS database), the method comprising receiving from a client apparatus an input data item including heading data identifying the input data item; correlating said heading data with a data field used in the PLCS database amongst all data fields used in the PLCS database thereby identifying a correlated entry in the PLCS database to be associated with the input data item; searching the PLCS database using said correlated entry; retrieving one or more data elements from the PLCS database according to said search; outputting to the client apparatus a return data item which includes said heading data identifying the return data item and which includes said retrieved data elements(s).

FIELD OF THE INVENTION

The invention relates to a system for improved data storage andretrieval, such as e.g. database systems and methods for through-lifemanagement of complex assets. In particular, though not exclusively, theinvention relates to information management and exchange systems forthrough-life management of complex assets such as navalvessels/vehicles, or the like.

BACKGROUND

Effectively managing all of the information related to production dataand maintenance process data needed to produce, and then support andmaintain a complex product Cassen is a difficult task. A significantproblem arises because, typically, any one of the potentially manyparticipants involved in such processes, do not have appropriate accessto information created by any of the other participants. As a result,information which already exists either has to be re-generated,re-formatted or re-entered manually with a proliferation of errors overtime, or managers are forced to make decisions based on incomplete orinaccurate information. The impact of information errors and omissionsadd heavy costs and time delays to manufacturing and maintenanceprocesses.

The invention aims to provide an improved database system and method forthrough-life management of complex assets.

BRIEF DESCRIPTION

At its most general, a concept of the invention is the means ofproviding a common database of optimal data/information (e.g.production, status and/or maintenance data) about a physical asset (e.g.vehicle, vessel, machine, product/item) gleaned/learned from datarelating to the asset submitted over a period of time by multipleseparate users. Each user may employ a different respective (local)schema, terminology or naming conventions relating to the self sameasset. Those disparate users are able to interrogate and/or update thecommon database using their respective (local) schema, terminology ornaming conventions. Accordingly, through a period of time, preferablyits lifetime, multiple disparate users may use the common databaseregarding a shared asset, without being required to know or use thedatabase schema of the common database, and the content of the databaseis optimised by selecting optimal data from amongst asset data submittedby the multiple users. The optimal data may preferably be optimal in thesense of being: more accurate or extensive in information contentnumerically and/or textually; expressed in a manner compliant withpredetermined or accepted terminology, schema or naming convention;containing fewer or no errors/typos (numerical and/or textual).

Information about an asset will, over time, typically be created in manydifferent locations using different local IT systems, databases and/orusers, each potentially using bespoke authoring tools and eachpotentially employing different schema, terminology and namingconventions relating to the self same asset. The invention allowsdifferent, disparate databases, and the users, to interact with (e.g.update, interrogate etc.) the common database each using a differentrespective (local), non-common database schema, naming convention orterminology. In this way, effective and useful access to informationabout the asset may be provided to different, disparate IT systems ordatabases, and the users of them. The invention allows the assetinformation to be consolidated while enabling direct access by disparateIT systems employing their disparate terminology and naming conventions.

Preferably, the invention may provide a data storage and retrievalsystem for a computer memory for maintaining the common database forproduct life cycle support. The common database may employ a PLCSdatabase schema. Thus, a PLCS schema may be used as a mapping betweensystems having a standardised data exchange capabilities.

The PLCS standard ISO 10303-239 (PLCS) is an international standard thatspecifies an information model that defines what information can beexchanged and represented to support a product through life. In thesystem or the method of the invention, in preferred aspects, the PLCSdatabase (schema) may be compliant with a PLCS open standard ISO10303-239. The invention, in any aspect herein, may provide a system ormethod in which the PLCS database is compliant with a PLCS open standardISO 10303-239.

In a first aspect, the invention may provide a data storage andretrieval system for a computer memory for maintaining a database forproduct life cycle support (PLCS database), comprising a computer orcomputer network system which:

receives two or more data exchange packets comprising data fields andpopulated with data according to different respective database schemawherein each received data exchange item comprises field headersassociated with respective said data fields according to a saidrespective database schema;

transforms one or more field headers of the received data exchangepackets into a common field header format according to a common domainmodel schema;

selects optimal data from amongst said data;

generates a master data exchange packet comprising said common fieldheaders as field headers of the master data exchange packet, and saidoptimal attribute data in data fields of the master data exchange packetin association with said field headers thereof;

maps the field headers of the master data exchange packet tocorresponding field headers of the PLCS database schema;

loads the optimal attribute data of the master data exchange packet intothe PLCS database according to the mapped PLCS field headers.

Thus, the invention may provide a data storage and retrieval system fora computer memory for maintaining a database for product life cyclesupport (PLCS database), comprising a computer or computer networksystem. The computer or computer network system is arranged to receivetwo or more data exchange packets comprising data fields and populatedwith data according to different respective database schema. Eachreceived data exchange item may comprise: identity data withinrespective said data fields identifying a respective entity; attributedata within respective said data fields identifying an attribute of eachentity, respectively; and, field headers associated with respective saiddata fields according to a said respective database schema. An/eachfield header may identify a particular domain (e.g.name/class/title/designation etc.) of an attribute, and all attributevalues associated with a given field header may belong to the sameattribute domain. Thus the field headers may collectively define thecollection of different attribute domains conveyed by the data exchangeitem. The attribute data may provide a particular value/property of thatdomain of attribute (field header) of an asset. For example, purely asan illustration of this principle, in a school database, a student maybe considered as an entity and his/her attributes include: Name; Age;Class No. etc. Each of these attributes has an attribute value for agiven student, and the collection of attribute values for any oneattribute (e.g. age) covering multiple students, defines the domain ofthat attribute. A field header, and/or an identity data and/or anattribute data may comprise a lexical item, or a numerical value/item,or a combination of both. Consequently, received data exchange packetsprovide the information defining how the sender of the packet chooses toidentify each item referred to in the packet (e.g. asset, or a part ofit, or information regarding its status/history).

Typically, these identity data items will be bespoke to the systemoriginating them, and are typically not the same as between differentsystems from which the two or more data exchange packets may originate.The attribute data items and/or field headers may be expressed in amanner bespoke to the system originating them. While attribute dataexpressing the self-same attribute of the common asset may beapproximately the same, as between two different originating senders ofthe received data exchange packets, given that they represent the sameproperty/attribute of the asset, they are often not exactly the same,e.g. with one being more precisely or fully expressed than the other.This is also often true of the received field headers identifying thenature of the attribute.

The computer or computer network system may select, for each saidentity, from amongst the attribute data the optimal attribute datathereof. The optimal data may preferably be determined to be optimalaccording to a predetermined selection criterion implemented by aselection algorithm. The algorithm may determine a data item as beingmore optimal than another in the sense of being: more accurate orextensive in information content numerically and/or textually; expressedin a manner compliant with predetermined or accepted terminology, schemaor naming convention; containing fewer or no errors/typos (numericaland/or textual). The computer or computer network system may map thefield headers of the master data exchange packet to corresponding fieldheaders of the PLCS database schema. The computer or computer networksystem may load the optimal attribute data of the master data exchangepacket into the PLCS database according to the mapped PLCS fieldheaders.

The invention may provide a domain model and its implementation, toallow easier and more user-friendly interaction with a PLCS databasesystem. The term ‘domain model’ is typically understood in the art torefer to a system of abstractions that describes selected aspects ofsome particular sphere or activity (a ‘domain’) undertaken by anindividual, or by an organisation of the like. The domain model might,for example, be a representation of meaningful real-world concepts thatrelate to the sphere of activity (the ‘domain’) that can be modelled insoftware. A domain model can be used to solve problems related to thatsphere of activity (the ‘domain’). The real-world concepts could includethe data generated/handled by an organisation and the rules which theorganisation uses in relation to handling that data. A domain modelgenerally uses the vocabulary of the sphere of activity (the ‘domain’)so that the software model can be used to communicate with non-technicalusers.

The domain model of the invention is preferably designed to support dataexchange with a PLCS system for specific activities, providing rules forhow to combine/correlate PLCS entities and external data items, or UserObjects, in that exchange. The User Object uses meaningful terms tospecify the possible content of any exchange. The computer or computernetwork system may be arranged to transform one or more field headers ofthe received data exchange packets into a common field header formataccording to a common domain model schema.

The computer or computer network system may be arranged to receive thedata exchange packets comprising: identity data (ID) within respectivesaid data fields identifying a respective entity; attribute data withinrespective said data fields identifying an attribute of each entity,respectively; and said computer or computer network system selects, foreach said entity, from amongst the attribute data the optimal attributedata thereof.

The computer or computer network system may be arranged to configure themaster data exchange packet for said computer memory according to alogical table including: a plurality of logical rows each correspondingto a record of information comprising said optimal attribute data, eachsaid logical row having two or more said identity data (ID) from thereceived data exchange packets which each separately identify the samesaid logical row; a plurality of logical columns intersecting saidplurality of logical rows to define a plurality of logical cells, eachsaid logical column having a respective field header to identify saidlogical column and in which at least one said logical column comprisessaid optimal attribute data. The computer or computer network system maymap the field headers of said logical table to corresponding fieldheaders of said PLCS database schema.

The logical table may be defined by, or in accordance with, a so-calledEntity-Relationship (ER) Logical Database Model. A relational modeldefines rules for organizing data items, adhered to by the databasemanagement system implementing it. In this way, the invention may recordreal-world scenarios into a database model, defining entities, theirentity data, and their attribute data. This allows relationships amongentities to be identified, encoded and accessed more efficiently in thedatabase. The logical association among entities is referred to in theart as a ‘relationship’. Relationships between entities may be mapped invarious ways, as would be readily apparent to the skilled person. Theprovision of a logical table according to a so-calledEntity-Relationship (ER) Logical Database Model, enables this inpreferred aspects of the invention. The logical table, and the datastored within it, may provide a so-called ‘relation’ table for arelational database. Each row in the relation table may represent aparticular entity, and each column may represent an attribute that isshared over all entities represented in that table.

The computer or computer network system may be arranged to generate themaster data exchange packet comprising said identity data (ID) from thereceived data exchange packets in association with corresponding saidentities of the master data exchange packet.

The computer or computer network system may be arranged to assign arespective priority value to each of said attribute data, and selectsthe attribute having the highest priority value as the optimalattribute. This aspect of the invention provides a degree of datacleansing whereby the host computer system of the PLCS database maymonitor when different terms are used by different users to refer to thesame asset. The host computer system may link these two different termsto the same single term employed in the PLCS database, and use thatsingle term to maintain/access/interrogate the PLCS database. Prioritiesmay be used by the host computer system to identify which one of severaldifferent user-originating terms, for the same asset, is the mostsuitable one to use as the ‘approved’ term in communications with clientapparatuses and their users. The host computer system may be arranged tocommunicate back to client apparatuses (and their users) informationfrom the PLCS database associated with the single term used therein, andmay use the ‘approved’ term within such communications to identify theasset to the client apparatus.

The method may include calculating a respective said priority value foreach of the first and second identifiers according to a combination of aplurality of priority weighting values determined according topredetermined characteristics of each of the first and secondidentifiers.

The method may include: retrieving from the PLCS database the entryassociated with the correlated data field; and, outputting to the secondclient apparatus a return data item which includes the second identifieridentifying the return data item and which includes the retrieved entry.

The computer or computer network system may be arranged to: receive adata retrieval request from a client apparatus employing a respectiveclient database schema; retrieve from the PLCS database said optimalattribute data; transform the common field header associated with theretrieved optimal attribute data into a field header format of theclient database schema; and, output to the client apparatus a returndata exchange packet which includes a data field with an associatedfield header in said format of the client database schema and populatedwith said retrieved optimal attribute.

In a second aspect, the invention may provide a method for data storageand retrieval in a computer memory for maintaining a database forproduct life cycle support (PLCS database), the method comprising:

receiving two or more data exchange packets comprising data fields andpopulated with data according to different respective database schemawherein each received data exchange item comprises field headersassociated with respective said data fields according to a saidrespective database schema;

transforming one or more field headers of the received data exchangepacket into a common field header format according to a common domainmodel schema;

selecting optimal data from amongst said data;

generating a master data exchange packet comprising said common fieldheaders as field headers of the master data exchange packet, and saidoptimal attribute data in data fields of the master data exchange packetin association with said field headers thereof;

mapping the field headers of the master data exchange packet tocorresponding field headers of the PLCS database schema;

loading the optimal attribute data of the master data exchange packetinto the PLCS database according to the mapped PLCS field headers.

In the method, the step of receiving may include receiving said dataexchange packets comprising: identity data (ID) within respective saiddata fields identifying a respective entity; attribute data withinrespective said data fields identifying an attribute of each entity,respectively. The step of selecting may include selecting, for each saidentity, from amongst the attribute data the optimal attribute datathereof.

The method may include configuring the master data exchange packet forsaid computer memory according to a logical table including: a pluralityof logical rows each corresponding to a record of information comprisingsaid optimal attribute data, each said logical row having two or moresaid identity data (ID) from the received data exchange packets whicheach separately identify the same said logical row; a plurality oflogical columns intersecting said plurality of logical rows to define aplurality of logical cells, each said logical column having a respectivefield header to identify said logical column and in which at least onesaid logical column comprises said optimal attribute data. The step ofmapping may map said field headers of said logical table tocorresponding field headers of said PLCS database schema.

The step of generating may include generating said master data exchangepacket comprising said identity data (ID) from the received dataexchange packets in association with corresponding said entities of themaster data exchange packet.

The method may include assigning a respective priority value to each ofsaid attribute data, wherein said selecting includes selecting theattribute having the highest priority value as the optimal attribute.

The method may include receiving a data retrieval request from a clientapparatus employing a respective client database schema, retrieving fromthe PLCS database said optimal attribute data, transforming the commonfield header associated with the retrieved optimal attribute data into afield header format of the client database schema and, outputting to theclient apparatus a return data exchange packet which includes a datafield with an associated field header in said format of the clientdatabase schema and populated with said retrieved optimal attribute.

In a further aspect, the invention may provide a data storage andretrieval system for a computer memory for maintaining a database forproduct life cycle support (PLCS database), comprising a computer orcomputer network system including: means for receiving two or more dataexchange packets comprising data fields and populated with dataaccording to different respective database schema wherein each receiveddata exchange item comprises: identity data within respective said datafields identifying a respective entity; attribute data within respectivesaid data fields identifying an attribute of each entity, respectively;field headers associated with respective said data fields according to asaid respective database schema; and means for transforming one or morefield headers of the received data exchange packets into a common fieldheader format according to a common domain model schema; means forselecting, for each said entity, from amongst the attribute data theoptimal attribute data thereof; means for generating a master dataexchange packet comprising: said common field headers as field headersof the master data exchange packet; said identity data from the receiveddata exchange packets in association with corresponding said entities ofthe master data exchange packet; said optimal attribute data in datafields of the master data exchange packet in association with said fieldheaders thereof; means for mapping the field headers of the master dataexchange packet to corresponding field headers of the PLCS databaseschema; means for loading the optimal attribute data of the master dataexchange packet into the PLCS database according to the mapped PLCSfield headers.

In another aspect, the invention may provide a data storage and/orretrieval system for a computer memory for maintaining a database forproduct life cycle support (PLCS database), comprising a computer orcomputer network system which:

receives two or more data exchange packets comprising data fields andpopulated with data according to different respective database schemawherein each received data exchange packet comprises:

identity data (ID) within respective said data fields identifying arespective entity;

attribute data within respective said data fields identifying anattribute of each entity, respectively;

selects, for each said entity, from amongst the attribute data theoptimal attribute data thereof;

configures said computer memory according to a logical table including:

a plurality of logical rows each corresponding to a record ofinformation comprising said optimal attribute data, each said logicalrow having two or more said identity data (ID) from the received dataexchange packets which each separately identify the same said logicalrow;

a plurality of logical columns intersecting said plurality of logicalrows to define a plurality of logical cells, each said logical columnhaving a respective field header to identify said logical column and inwhich at least one said logical column comprises said optimal attributedata;

wherein the computer or computer network system maps said field headersof said logical table to corresponding field headers of said PLCSdatabase schema.

In yet another aspect, the invention may provide a computer programproduct comprising computer-executable instructions arranged to controla computer to implement the method of any aspect described above, whenexecuted on the computer.

In an aspect, the invention may provide a method for providing access toa database for product life cycle support (PLCS database), the methodcomprising, receiving from a client apparatus an input data itemincluding heading data identifying the input data item, correlating theheading data with a data field used in the PLCS database amongst alldata fields used in the PLCS database thereby identifying a correlatedentry in the PLCS database to be associated with the input data item,searching the PLCS database using the correlated entry, retrieving oneor more data elements from the PLCS database according to the search,outputting to the client apparatus a return data item which includes theheading data identifying the return data item and which includes theretrieved data elements(s).

The method may include receiving one or more data element(s) within thereceived input data item; and, searching the PLCS database using thecorrelated entry; and, entering a received data element as a new dataelement of the PLCS database at a location therein determined accordingto the search.

The heading data may correspond to a data field from a client database,the method including subsequently correlating the one or more retrievedPLCS data elements with the data field from the client database therebyidentifying a correlated entry from the client database to be associatedwith the one or more retrieved PLCS data elements, and subsequentlyoutputting the return data item.

The method may include providing a mapping database containing aplurality of client headings data from a client database and a pluralityof PLCS headings data used in the PLCS database, wherein each saidclient headings data item is stored in the mapping database inassociation with respective PLCS headings data, and the correlatingincludes searching the mapping database to identify a said association.

In an aspect, the invention may provide a system for providing access toa database for product life cycle support (PLCS database), the systemcomprising, a communications network; a storage device including a PLCSdatabase PLCS data elements and arranged in communication with thecommunications network; a client device arranged in communication withthe communications network; a host computer system arranged incommunication with the communications network and with the storagedevice, wherein the host computer system is arranged to implement amethod comprising: receiving an input data item (e.g. data exchangepacket) from the client device via the communications network, the inputdata item including headings data associated with a data element(s)within the input data item/packet; correlating the heading data withheadings data used in the PLCS database thereby identifying a correlatedentry in the PLCS database to be associated with the input data element;searching the PLCS database using the correlated entry; retrieving oneor more data elements from the PLCS database according to the search;outputting to the client a return data packet which includes the headingdata identifying the return data item and which includes the retrieveddata elements(s).

The host computer system may be arranged to implement the methodincluding receiving one or more user data element(s) within the receivedinput data item/packet; and, searching the PLCS database using thecorrelated entry; and, entering a client data element as a new dataelement of the PLCS database at a location therein determined accordingto the search.

The heading data may correspond to a data heading from a clientdatabase, and the host computer system may be arranged to implement themethod including: subsequently correlating the one or more retrievedPLCS data elements with the heading from the client database therebyidentifying a correlated entry from the client database to be associatedwith the one or more retrieved PLCS data elements, and subsequentlyoutputting the return data item/packet.

The system may include a mapping database containing a plurality ofclient heading data items from a client database and a plurality of PLCSheadings used in the PLCS database, wherein each said client headingdata item is stored in the mapping database in association with arespective PLCS headings, and the host computer system is arranged toimplement the method such that the correlating (and the subsequentcorrelating) includes searching the mapping database to identify a saidassociation.

In an aspect, the invention may provide a method for communicating witha database for product life cycle support (PLCS database), the methodcomprising: receiving from a first client apparatus a firstcommunication containing an input data item for entry in the PLCSdatabase and a first identifier identifying the input data item;correlating the first identifier with a data field (e.g. header(s);attributes data field(s)) used in the PLCS database amongst all datafields used in the PLCS database thereby identifying a correlated datafield of the PLCS database to be associated with the input data item;searching the PLCS database to access an entry therein associated withthe correlated data field; updating the entry of the PLCS databaseaccording to the input data item; re-correlating the correlated datafield of the PLCS database with a second identifier associated with asecond client apparatus; outputting to the second client apparatus asecond communication containing an output data item according to theupdated PLCS database entry which includes the second identifieridentifying the output data item to the second client apparatus.

In this way, a first client apparatus may access the PLCS database andupdate/modify that database, and the host computer system in control ofthe PLCS database may then generate a communication of thatupdate/modification to be sent to a second client apparatus. The hostsystem may keep track of the changes to the PLCS database and notifyinterested other client apparatuses (e.g. remote sites, databases orcomputer systems). For example, a first client apparatus may include auser-interface (e.g. interactive graphic) in which user-inputs may beperformed, which may cause the first client apparatus to generate datafor entry into the PLCS database, to update/modify the database. Forexample, a user of the first client apparatus may wish to update thePLCS database to indicate that an event, task or job has been started,or completed, in respect of a particular project of work in which manydisparate users are involved. A PLCS database update may, for example,occur to indicate completion/commencement of a process stage within alarger work project. As the project progresses a user may input thisfact into the PLCS database via the user interface local to them, toindicate progression of steps within the work-flow. The invention, inthis aspect, may permit that when a process stage is completed, the PLCSdatabase may be updated, and that update may be communicated to otherclient apparatuses (e.g. outside sites, e.g. another shipyard's computersystem) in a language that the computer system of that outside site canunderstand. The invention, in this aspect, relates to ‘correlation’simply to allow a first client apparatus (and its user) to access toPLCS without needing to ‘understand’ the PLCS terminology/language. The‘correlating’ step implemented by the invention, in this aspect, isthereby used in allow updating data to enter the PLCS database, and alsoto use the updated PLCS database to generate an update message, totransmit to the interested third parties (second client apparatus) toallow that third party to update its own local database directly in a‘language’ it understands (i.e. using the ‘re-correlation’ process).

The method may include receiving one or more data element(s) within thereceived input data item; and, searching the PLCS database using thecorrelated entry; and, entering a received data element as a new dataelement of the PLCS database at a location therein determined accordingto the search.

The first identifier may correspond to a data field (e.g. header(s);attributes data field(s)) from a first client database, and the secondidentifier may correspond to a data field (e.g. header(s); attributesdata field(s)) from a second client database whereby the re-correlatingidentifies a correlated entry from the second client database to beassociated with the updated PLCS data field.

The method may include providing a mapping database containing aplurality of identifier data items (e.g. header(s)) from a clientdatabase and a plurality of data fields (e.g. header(s); attributes datafield(s)) used in the PLCS database, wherein each said identifier dataitem is stored in the mapping database in association with a respectivesaid data field, and the correlating includes searching the mappingdatabase to identify a said association.

The method may include providing a mapping database containing aplurality of identifier data items (e.g. header(s); attributes datafield(s)) from a client apparatus and a plurality of data fields used inthe PLCS database, wherein each said data field is stored in the mappingdatabase in association with a respective said identifier data item, andthe subsequent re-correlating includes searching the mapping database toidentify a said association.

The invention in another aspect may provide a system for providingaccess to a database for product life cycle support (PLCS database), thesystem comprising: a communications network; a storage device includinga PLCS database PLCS data elements and arranged in communication withthe communications network; a plurality of client apparatuses arrangedin communication with the communications network; a host computer systemarranged in communication with the communications network and with thestorage device, wherein the host computer system is arranged toimplement a method comprising: receiving from a client apparatus acommunication containing an input data item for entry in the PLCSdatabase and an identifier identifying the input data item (e.g.header(s); attributes data field(s)); correlating the identifier with adata field used in the PLCS database amongst all data fields used in thePLCS database thereby identifying a correlated data field of the PLCSdatabase to be associated with the input data item; searching the PLCSdatabase to access an entry therein associated with the correlated datafield; updating the entry of the PLCS database according to the inputdata item; re-correlating the correlated data field of the PLCS databasewith a second identifier (e.g. header(s); attributes data field(s))associated with a second client apparatus; outputting to the secondclient apparatus a communication containing an output data itemaccording to the updated PLCS database entry which includes the secondidentifier identifying the output data item to the second clientapparatus.

The host computer system may be arranged to implement a methodincluding; receiving one or more data element(s) within the receivedinput data item; and, searching the PLCS database using the correlatedentry; and, entering a received data element as a new data element ofthe PLCS database at a location therein determined according to thesearch.

The first identifier may correspond to a data field from a first clientdatabase, and the second identifier may correspond to a data field froma second client database whereby the re-correlating identifies acorrelated entry from the second client database to be associated withthe updated PLCS data field.

The host computer system may be arranged to implement a method includingproviding a mapping database as described above for use in thecorrelating/re-correlating steps.

In a yet further aspect, the invention may provide a computer programproduct comprising compute-executable instructions arranged to control acomputer to implement the method of any of the above aspects whenexecuted on the computer.

In another aspect, the invention may provide a computer, or a system ofcomputers, or a network of computers, programmed to implement the methodof any of the above aspects. The term ‘system’ herein may refer to, orinclude, e.g. a network of computers, which may be connected incommunication via a communications network (e.g. an intranet or theInternet).

According to aspects of the invention, User Objects may be “mapped” to acentral database (e.g. PLCS). This mapping may be represented byLook-up-Tables or Templates. Each User Object may have a correspondingTemplate that specifies how the User Object is represented using thecentral database (e.g. PLCS). Having mapped the User Object to thecentral database (e.g. PLCS), the complete central database (e.g. PLCS)that is required by the user is identified using naming-convention termscompatible with the user's database system.

There now follow examples of the many and various embodiments of theinvention. These describe embodiments which are useful for a betterunderstanding of the invention, but which are not intended to belimiting.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically shows a network system for implementing anembodiment of the invention;

FIG. 2 schematically shows a detailed view of a part of the networksystem of FIG. 1;

FIG. 3 illustrates a data exchange packet containing header fields andattributes fields associated with them;

FIG. 4 schematically shows a system for implementing an embodiment ofthe invention;

FIG. 5 schematically shows a more detailed view of FIG. 4;

FIG. 6 schematically shows the local transformation process applied todata exchange packets input to the database system from two separateclient apparatuses, to provide transformed data exchange packets sharingreplacement headers in common;

FIG. 7 schematically shows the process of data cleansing by selectingoptimal attributes from the two transformed data exchange packets foruse in one master data exchange packet for mapping to the PLCS database.

DETAILED DESCRIPTION

In the drawings, like items are assigned like reference symbols.

FIG. 1 schematically illustrates a networked system (1) of databases andcomputers according to an embodiment of the invention. The systemcomprises a communications network (2), such as an intranet or theInternet, to which are linked a first shipyard (3) and a second,separate shipyard (4). Both shipyards contain respective shipmaintenance records containing data and information concerning themaintenance history for each vessel that has entered the shipyard inquestion for maintenance. Maintenance records might include, forexample, a service history containing information such dates when avessel entered the shipyard, the identity of the vessel, the workperformed on the vessel by the shipyard staff, reports of shipyard staffconcerning outcomes/assessments of the vessel and/or work done on thevessel by them, components within the vessel replaced whilst in theshipyard, or identified as requiring replacement, etc.

Both shipyards also contain respective stock records containing data andinformation concerning the stock of components and spare parts held bythe shipyard at a given time. Components and spare parts might includethose suitable for maintaining and servicing ships entering the shipyardfor that purpose (e.g. engine parts, ship's equipment, components forpower a ship's supply system, ship's communication components etc.).

This information, both maintenance history and stock records, regardingthe first shipyard (3), is contained in a first database (5) of thefirst shipyard, and controlled by a first computer system (6) of thefirst shipyard. Similarly, maintenance history and stock recordsregarding the second shipyard (4), is contained in a second database (7)of the second shipyard, and is controlled by a second computer system(8) of the first shipyard.

The first and second databases, of the first and second shipyards, areeach arranged and constructed such that the data and information withinthem contains headings data identifying the user data elements. Forexample, the first and second shipyards may each employ a heading,amongst many other headings, identified as “NatoStockNo.” whichindicates that the data entry associated with that heading relates toinformation concerning a ship's part (e.g. a pre-defined 3^(rd) partystock numbering system; etc.). Similarly, in another example, whereasthe first shipyard may employ a heading identified as “Part Title” or“Weight”, the second shipyard may employ a heading identified as “AssetTitle” or “Mass” for the very same object (an engine or rudder of aship). A User Object (14) may be regarded as a packet (for transmission)comprising headings and containing a attributes data elements, and thefirst and second computer systems of the first/second shipyards arearranged to transmit and receive User Objects from central data system(10) via a network (2). Within each User Object, the user data elementcomprises/identifies data/information associated with that heading (e.g.a stock number; the part title; its weight, etc.)

The central data system comprises a PLCS database (13) managed andcontrolled by a PLCS computer system (12). The PLCS database comprisesdata elements/entries according to a PLCS database domain model andnaming convention. The central data system is arranged in communicationwith the communications network to permit communication with the firstand/or second shipyards.

Optionally, an external computer device (9) may be arranged incommunication with the communications network for communicating with thecentral data system and the PLCS database within it. This allows thirdparties (e.g. another shipyard, or an administrator) access to thecentral data system, such as for transmitting and/or receiving UserObjects (14).

The central data system comprises a host computer system (11) referredhereafter as a “correlator unit”. The correlator unit is arranged incommunication with the communications network and with the PLCS computersystem (12) and thereby with the PLCS database. The correlator unit isarranged to implement a receive a User Object (14) from the first/secondshipyard computer system (or optionally from the external computerdevice (9)) via the communications network. The User Object includesheading data and user data elements (e.g. attributes) within the UserObject in association with the heading data.

The correlator unit is arranged to correlate the heading data of theUser Object with heading data used in the PLCS database therebyidentifying a correlated entry in the PLCS database to be associatedwith the User Object. A method of correlating data headings of a UserObject (which uses a shipyard's database domain model schema and recordnaming convention) with heading data of the PLCS database, isschematically shown in FIG. 3. The correlator unit (11) contains a map(30) comprising a collection of heading data classified as “PLCSdatabase headings” and these data fields list the terminology for dataobjects (e.g. attribute data) according to the PLCS domain model schemaand naming convention. The map (30) also contains a collection of datafields classified as “first database headings” and another collection ofdata fields classified as “second database headings”, and thesecollections of data fields list the terminology for headings accordingto the domain model schema and naming convention employed by the firstdatabase and by the second database, respectively, of the first andsecond shipyard. The domain model schema and naming conventions of thefirst and second databases differ from each other and each also differsfrom the PLCS domain model schema and naming convention employed by thePLCS database (13).

The map is constructed and arranged to directly associate a givenfirst/second database heading data with an associated or correspondingPLCS database heading data. This enables the correlator unit to, ineffect, translate a term/name/heading compliant with the domain modelschema and naming convention of any one the first database, seconddatabase and PLCS database domain model schema and naming conventions,into any associated/corresponding term/name compliant with the domainmodel schema and naming convention of any other one the first database,second database and PLCS database domain model schema and namingconventions. The map may store all corresponding terms/names inassociation with each other in the manner of a look-up-table, ordictionary of terms, and/or may employ pointers stored in the correlatorunit in association with term/name which points to each of the one ormore corresponding terms/names stored in the correlator unit.

The PLCS system (12) is arranged to receive from the correlator unit thecorrelated entry obtained from the map (30) and to search the PLCSdatabase using that correlated entry, and retrieve one or more dataelements from the PLCS database according to that search. The correlatedentry will be expressed in terms compliant with the PLCS domain modelschema and naming convention and so this enables the PLCS system toperform searching of the PLCS database directly using the correlatedentry obtained from the map (30) by the correlator unit.

The PLCS system is arranged to output to the first/second shipyard (i.e.the ‘user’) a return User Object which includes the heading dataidentifying the return User Object according to the naming convention ofthe shipyard in question and which includes the retrieved dataelements(s) e.g. attribute values.

As a result of the process of correlation, the translator unit enablesmeaningful communication and data access (e.g. searching, input,retrieval) with the PLCS database to take place from either one of thetwo shipyards despite the fact that the two shipyards employ differentnaming conventions for common objects/actions/data items. The effect isthat the first or second shipyard is able to “speak to” the PLCS system(12) using the “language” (i.e. domain model schema and namingconvention) understood by the first/second shipyard, and make full useof the PLCS database in spite of the fact that the PLCS database uses adifferent “language” (i.e. domain model schema and naming convention).Similarly, PLCS system is able to “speak to” the first/second shipyardusing the “language” (i.e. domain model schema and naming convention)understood by that shipyard, in spite of the fact that the shipyards'databases each use a different “language” (i.e. domain model schema andnaming convention). The translator unit may, conceptually, be regardedas a “filter” though which any one shipyard is able to “speak” to thePLCS system in its own “terms”, and vice versa.

The PLCS computer system (12) is also arranged to receive one or more ofthe user data element(s), e.g. attribute values, contained within thereceived User Object (14) and enter one or more of those user dataelements as a new data element of the PLCS database at a locationtherein determined according to the search done using the correlatedentry.

Because the heading data corresponds to a heading from a shipyard'sdatabase, in providing a return User Object, the correlator unit isarranged to use the map (30) to correlate the one or more retrieved PLCSdata elements (using the PLCS heading associated with them) with a datafield from the user database thereby identifying a correlated entry fromthe shipyard's database. This correlated heading is then associated withthe one or more retrieved PLCS data elements, and used in the returnUser Object subsequently output.

The PLCS computer system and PLCS database are each compliant with thePLCS open standard ISO 10303-239.

This two-way system for correlating heading data (generically: “A”; “B”;“C”; . . . ) of the domain model schema and naming convention of ashipyard to the heading data (generically: “α”; “β”; “γ”; . . . ) of aPLCS database, to permit receipt and transmission of User Objects andreturn User Objects, is schematically illustrated in FIG. 2. Thegenerically-represented map (30) of FIG. 2 relates to the more specific(non-limiting) example of FIG. 3 as follows:

A=“Part Title”→α=“Asset Slot Title”

B=“Weight”→β=“Mass (kg)”

C=“Color”→γ=“Colour”

FIG. 4 schematically shows an embodiment of the invention. This figureshows a networked computer system similar to the system of FIG. 1. Thissystem is arranged to provide access to a PLCS database, and includes astorage device (13) including a PLCS database of PLCS data elementsarranged in communication with a communications network (2). Two clientapparatuses (3, 4) are arranged in communication with the communicationsnetwork for accessing the PLCS database. A host computer system (23) isarranged in communication with the communications network and with thestorage device. The host computer system is arranged to receive from anyone of the two client apparatus (3, 4) a communication (e.g. dataexchange packet), via the network (2), containing input data items forentry in the PLCS database and headers associated with them. The headersare expressed according to the domain model schema of the clientapparatus, which is typically not a PLCS format. The host computer isarranged to correlate the headers contained within the receivedcommunication, with headers used in the PLCS database (e.g. amongst allheaders used in the PLCS database). This occurs using a mappingprocedure carried out by a mapping unit (11) of the host computer, suchas is described above.

The host computer system includes a plurality (two shown here) ofuser-specific translators (15, 16) each one of which is arranged incommunication with a respective one of the client apparatuses (3, 4) viathe network (2). Each user-specific translator is arranged to initiallymap between headers of the communication from its respective clientapparatus, received in a domain model schema associated with that clientapparatus, and a replacement header format according to a respectiveclient format mapping. This mapping is defined by a domain model whichdefined the correlation between the format/naming-convention of therespective client apparatus to the replacement header format/namingconvention. This replacement header format is the format employed by thehost computer system to correlate with, or map to, the PLCS domain modelschema.

Thus, a first user-specific translator (15) is provided for mappingcontent of the communications from/to a first client apparatus (3)from/to a format associated with the first client apparatus to/from thereplacement header format according to a first client format mapping(e.g. a first domain model). A second user-specific translator (16) isprovided for mapping content of the communications from/to a secondclient apparatus (4) from/to a format associated with the second clientapparatus to/from the replacement header format according to a secondclient format mapping (e.g. a second domain model).

The host computer system also includes a mapping unit (11) arranged formapping/translating the replacement headers from the client apparatuses,to headers used in the PLCS database. The mapping is performed from thereplacement header format (e.g. a domain model) to the PLCS domain modelschema and format when inputting new data to the PLCS database, and inreverse order when outputting data from it.

Thereby, the host computer is able to identify a correlated data fieldof the PLCS database to be associated with the input data item (e.g.attribute value). In other words, the PLCS mapping unit (11) is able totranslate from the format of the received communication, into the formatof the PLCS database system.

Once mapped, the host computer system is arranged to search the PLCSdatabase (13) to access an entry therein associated with the correlateddata field within the communication received from the user apparatus(3), and to update the entry of the PLCS database according to the inputdata item. In this way, the host computer system is able to permit anon-PLCS formatted data entry to be submitted to the PLCS database bythe client apparatus (3), and to update the PLCS database appropriatelywith the information in a PLCD format.

Furthermore, the host computer system is also arranged to operate areverse process whereby another, second, client apparatus (4) may benotified of the new entry made in the PLCS database by first clientapparatus (3). To do so, the host computer system retrieves the updatedPLCS data entry from the PLCS database, and re-correlates the correlateddata field of the PLCS database with a second identifier associated witha second client apparatus (4). This re-correlation is done by the PLCSmapping unit (11) which maps the retrieved PLCS data entry into theintermediate domain model format, and then translates the result intothe user-specific format using the translator unit (16) associated withthe second client apparatus. The host computer system outputs to theresult to the second client apparatus via the network (2). Thecommunication so output contains an output data item according to theupdated PLCS database entry which includes a second identifieridentifying the output data item to the second client apparatus (i.e. ina format it can read/understand).

Thus, in this way the first header in the communication from the firstclient apparatus (3) may correspond to headers from a first clientdatabase (5), and the second header in the communication from the secondclient apparatus (7) may correspond to headers from a second clientdatabase. The re-correlating identifies a correlated entry from thesecond client database to be associated with the updated PLCS datafield.

Indeed, the PLCS database may be accessed by other client apparatuses(9) which may be arranged to be compatible with the common replacementdomain model format employed by the host computer system, therebyobviating the need for user-specific translators for communicationsto/from such other client apparatuses. This communication may be via adomain model Application Program Interface (API, 18). For example,‘dimensional model’ databases (19)—e.g. arranged to generatetime-dependent trends/forecasts in data—may access the PLCS database viathe correlator unit using the intermediate domain model format, in orderto provide business intelligence (BI) analysis and modelling (20) andapplications (21). These may be very useful in predicting futurerequirements/needs of the asset in question, by enabling forwardprediction. This is made feasible by having access to a PLCS databasewith up-to-date and reliable data provided by multipleusers/client-apparatuses.

In practice, different client apparatuses employ different headers toidentify the same item/asset represented in the PLCS database. Thesedifferent headers may change over time as different user apparatuseswishing to access the PLCS database may tend not to coordinate theirheaders amongst each other, and each apparatus is controlled by anindependent organisation employing its own domain model schema onidentifying relevant assets represented in the PLS database. Thesedomain model schema often change and evolve over time. To address this,the host computer system may be arranged to assign a respective priorityvalue to each of the first and second identifiers and to employ in thePLCS database the identifier having the highest priority value as thecommon identifier. In this way, the host computer system may be keptup-to-date with naming trends and reduce the risks of using obsoleteheaders.

The host computer system may implement algorithms for calculating arespective priority value for each of the first and second headersaccording to, for example, a combination of a plurality of priorityweighting values determined according to predetermined characteristicsof each of the first and second headers. For example, a priority valuemay be calculates according to an assessment of one or morecharacteristics, selected from a predetermined number ofcharacteristics. An example of suitable characteristics is as follows:

-   -   (1) Is the client apparatus associated with the second header        more trustworthy (e.g. less error prone, historically; e.g.        known to the system for longer) than the client apparatus        associated with the first header? If so then use the second        header.    -   (2) Is there no entry in the header associated with the first        client apparatus? If so, then use the second header.    -   (3) Is the first header incomplete/corrupted? If so, then use        the second header.    -   (4) Has the first header not been employed/used/seen in a data        exchange packet for more than a preceding specified period of        time (e.g. a year). If so then use the second header (e.g. the        first header likely out of date).

The algorithm may implement any one or more of interrogations (1) to (4)and if all individually result in a conclusion to use the second header,then on that condition the outcome may be to use the second header.

In this way data may be ‘cleansed’ by algorithmically selecting theoptimal (highest priority) header from amongst any two headers socompared. This means that poor, out or date, or otherwise sub-optimalheaders may be gleaned through the on-going use of the system so thatthe system auto-learns/auto-updates and optimises the interface with thePLCS database making it more robust and reliable to use by multipleusers/client apparatus.

This process is schematically illustrated in FIG. 5 which shows a moredetailed view of FIG. 4, and is supported by FIG. 6 and FIG. 7 asfollows. The input data exchange packets (15, 16) from the two separateclient apparatuses (3, 4) are transformed to provide transformed dataexchange packets (30, 31) sharing replacement headers in common. Datacleansing is then applied to these two transformed data exchange packetsby selecting optimal attributes from the two transformed data exchangepackets for use in one master data exchange packet 32 for mapping to thePLCS database 13.

In particular, the computer or computer network system receives two dataexchange packets (15, 16) each comprising data fields (34, 35) andpopulated with data according to different respective database schema.Each data exchange packets comprises identity data (ID) (see item 15,16: first, leftmost column of the logical table) within respective datafields identifying a respective entity. For example, ID values of: 1, 2,3, 4 are used in data exchange packet 15 to identify separate entities.For example, ID values of: A, B, C, D are used in data exchange packet16 to identify separate entities. Attribute data (see item 15, 16:second to fifth columns of the logical table) resides within respectivedata fields identifying an attribute of each entity, respectively.

Each received data exchange item comprises field headers (33, 38)associated with respective the data fields according to the respectivedatabase schema. The system is arranged to transform one or more fieldheaders 33 of the received data exchange packets (15, 16) into a common,replacement field header format according to a common domain modelschema. In the transformation process, data values remain the same, butthe data's schema is transformed to the new Domain Model's schema.

Referring to FIG. 7, the system selects, for each entity, from amongstthe attribute data of the two transformed data exchange packets (30,31), the optimal attribute data thereof, and generates a master dataexchange packet 32 comprising the common field replacement headers asfield headers of the master data exchange packet, and including theselected optimal attribute data in data fields of the master dataexchange packet in association with its field headers. Thisdata-cleansed data exchange packet is then ready to be used inconjunction with the PLCS database. In particular, the system isarranged to generate the master data exchange packet comprising theidentity data (‘Local ID’: e.g. ‘PartID’ and ‘AssetID’) from thereceived data exchange packets in association with correspondingentities of the master data exchange packet.

The system is arranged to map the field headers of the master dataexchange packet to corresponding field headers of the PLCS databaseschema, and to load the optimal attribute data of the master dataexchange packet into the PLCS database according to the mapped PLCSfield headers. This process is illustrated in FIG. 7 as a ‘Master DataManagement’ process in which similar records are matched via globalidentifiers (e.g. NatoStockNo), or via data values. Algorithms are usedto extract the preferred data from the systems (e.g. Client 1 (packet30) has more accurate Mass data, but Client 2 (packet 31) uses BritishEnglish).

As a result, the system may receive the two or more data exchangepackets (15, 16) which each contain identity data (‘Local ID’) withinrespective data fields identifying a respective entity, and attributedata within respective data fields identifying an attribute of eachentity, respectively. It may select, for each entity, from amongst theattribute data, the optimal attribute data, and configure the computermemory of the system according to a logical table represented by themaster data exchange packet 32. This includes:

-   -   a plurality of logical rows 39 each corresponding to a record of        information comprising the optimal attribute data. Each logical        row has two or more of the ‘Local ID’ identity data (PartID=4;        AssetID=D) from the received data exchange packets which each        separately identify the same logical row;    -   a plurality of logical columns 40 intersecting the plurality of        logical rows to define a plurality of logical cells, each        logical column having a respective field header (e.g. ‘Mass        (kg)’) to identify the logical column and in which at least one        logical column comprises optimal attribute data.

The computer or computer network system is arranged to map the fieldheaders of the logical table to corresponding field headers of the PLCSdatabase schema. By retaining the ‘Local ID’ attribute values andassociated headers, the system is able to immediately identify theoriginating source from which the optimal data was selected. RetainingLocal IDs is particularly useful for the following reasons. The Local IDmay be used by the computer system of the invention as the means ofidentifying an object for the Client (both in the local database of theClient apparatus and in the PLCS database). The Client apparatus maysubsequently refer to that same entity by/using their Local ID. Notethat the local Client apparatus is unlikely to start using any PLCSderived ID as a Client apparatus need not (and very likely does not wishto) concern itself with the PLCS system. One may consider any/all localClient systems to be entirely parochial. This means that the computersystem of the invention may be such that it does not need to identify anitem by tenuous, parochial identifiers such as names, which is likely tochange over time and is not a guaranteed identifier.

By retaining the Local ID, the computer system of the invention mayprovide that if a Client apparatus subsequently provides the computersystem with an update to the entity (e.g. if the attribute is a weightvalue, then it changes that weight value), the invention allows one toretrieve the entity from the PLCS database via the Local ID for theClient because the system has that data, and then to run the PLCS-helddata alongside the newly arrived/updated data against the same MDMalgorithms (see 17, FIG. 5) used previously. If the new data from theClient acquires a suitably high priority, then the computer system mayupdate the PLCS database with the new data. Thus, by holding the LocalID enables the computer system with implementing the following:

1. Further updates from the Client apparatus—as described above;

2. Requests for data—e.g. if the Client apparatus wants to know what the‘assured’ data for a given entity is, it can provide its Local ID andthe computer system may identify that in terms suitable for the PLCSdatabase, so that the latter will ‘know’ which entity is being talkingabout. The computer system nay then provide that sought—afterinformation back to the enquiring Client apparatus via an applicationprogram interface (API) providing an interface to the PLCS system forclient applications (see FIG. 5, “Feedback”);

3. Tracking sources—the PLCS database may be used to track from whichsystem it received changes, by linking the change to the Client's LocalID.

The embodiments described herein are presented so as to allow a betterunderstanding of the invention, and are not intended to limit the scopeof the inventive concept of the invention. Variations, modifications andequivalents to the embodiments described herein, such as would bereadily apparent to the skilled reader, are intended to be encompassedwithin the scope of the invention.

The invention claimed is:
 1. A method for providing access to a databasefor product life cycle support (PLCS) database), the method comprising:receiving from a first client apparatus an input data item includingheading data associated with a first database schema and identifying theinput data item; correlating said heading data with a data field used inthe PLCS database, the PLCS database having a second database schemadifferent from the first database schema, thereby identifying acorrelated entry in the PLCS database to be associated with the inputdata item; searching the PLCS database using said correlated entry;entering a received data element from the input data item as a new dataelement of the PLCS database at a location therein determined accordingto said search; retrieving one or more data elements from the PLCSdatabase according to said search; correlating said one or moreretrieved data elements from the PLCS database having the seconddatabase schema with a return data item having heading data associatedwith a third database schema different from the first and seconddatabase schemas; and outputting to a second client apparatus the returndata item which includes said heading data associated with the thirddatabase schema.
 2. The method according to claim 1, wherein thereceived input data item includes a plurality of data elements.
 3. Themethod according to claim 1, including providing a mapping databasecontaining a plurality of heading data items from a client databasehaving the first database schema and a plurality of data fields used inthe PLCS database, wherein each said heading data item is stored in themapping database in association with a respective said data field, andsaid correlating said heading data includes searching said mappingdatabase to identify a said association.
 4. The method according toclaim 1, including providing a mapping database containing a pluralityof heading data items from a client database having the third databaseschema and a plurality of data fields used in the PLCS database, whereineach said data field is stored in the mapping database in associationwith a respective said heading data item, and said correlating said oneor more retrieved data elements includes searching said mapping databaseto identify a said association.
 5. The method according to claim 1,including: receiving from the first client apparatus a firstcommunication containing a first identifier identifying data for entryin the PLCS database; receiving from the second client apparatus asecond communication containing a second identifier different from thefirst identifier and identifying data for entry in, or retrieval from,the PLCS database; comparing the second identifier to the firstidentifier; and in response to the comparison identifying a commonalitybetween the second identifier and the first identifier, determining thatboth the second identifier and the first identifier correspond to acommon data entry in the PLCS database, mapping the second identifierand the first identifier to a common identifier for the PLCS database,and accessing the PLCS database using the common identifier according tothe second communication.
 6. The method according to claim 5, in whichthe second communication further contains second data for entry in thePLCS database, and said accessing includes entering the second data intothe PLCS database at a location therein according to the commonidentifier.
 7. The method according to claim 5, in which the firstcommunication contains first data and the second communication furthercontains a request for retrieval of the first data in the PLCS database,and said accessing includes retrieving the first data in the PLCSdatabase from a location therein identified according to the commonidentifier.
 8. The method according to claim 5, including: mappingcontent of the first communication from a format associated with thefirst client apparatus to an intermediate format according to a firstclient format mapping; and mapping content of the second communicationfrom a format associated with the second client apparatus to saidintermediate format according to a second client format mapping; whereinthe mapping of the second identifier and the first identifier to acommon identifier for the PLCS database is performed in respect of saidintermediate format.
 9. The method according to claim 5, includingassigning a respective priority value to each of the first and secondidentifiers and employing in the PLCS database the identifier having thehighest priority value as the common identifier.
 10. The methodaccording to claim 9, in which a highest priority value amongst thepriority values assigned to the first and second identifiers is assignedto the identifier most recently received.
 11. The method according toclaim 9, including calculating a respective said priority value for eachof the first and second identifiers according to a combination of aplurality of priority weighting values determined according topredetermined characteristics of each of the first and secondidentifiers.
 12. The method according to claim 9, wherein assigning arespective priority value to each of the first and second identifierscomprises determining if the second client apparatus associated with thesecond identifier is more trustworthy than the first client apparatusassociated with the first identifier.
 13. A system for providing accessto a database for product life cycle support (PLCS) database), thesystem comprising: a storage device including a PLCS database havingPLCS data elements and arranged for communication with a communicationsnetwork; and a host computer system arranged for communication with thecommunications network and with the storage device, wherein the hostcomputer system is arranged to receive an input data item from a firstclient device via the communications network, the input data itemincluding heading data associated with a first database schema andidentifying the input data item, correlate said heading data with a datafield used in the PLCS database, the PLCS database having a seconddatabase schema different from the first database schema, therebyidentifying a correlated entry in the PLCS database to be associatedwith the input data item, search the PLCS database using said correlatedentry, enter a received data element from the input data item as a newdata element of the PLCS database at a location therein determinedaccording to said search, retrieve one or more data elements from thePLCS database according to said search, correlate said one or moreretrieved data elements from the PLCS database having the seconddatabase schema with a return data item having heading data associatedwith a third database schema different from the first and seconddatabase schemas, and output to a second client device the return dataitem which includes said heading data associated with the third databaseschema.
 14. The system according to claim 13, wherein the host computersystem is arranged to: receive a plurality of client data elementswithin the received input data item.
 15. The system according to claim13, wherein the host computer system comprises a mapping databasecontaining a plurality of heading data items from a client databasehaving the first database schema and a plurality of data fields used inthe PLCS database, wherein each said heading data item is stored in themapping database in association with a respective said data field, andwherein the host computer system is arranged to search said mappingdatabase to identify the correlated entry in the PLCS database to beassociated with the input data item.
 16. The system according to claim13, further comprising the first client device and the second clientdevice.
 17. A computer program product including one or morenon-transitory machine-readable mediums encoded with instructions thatwhen executed by one or more processors cause a process to be carriedout for communicating with a database for providing access to a databasefor product life cycle support (PLCS) database database), the processcomprising: receiving an input data item from a first client device viathe communications network, the input data item including heading dataassociated with a first database schema and identifying the input dataitem; correlating said heading data with a data field used in the PLCSdatabase having a second database schema different from the firstdatabase schema, thereby identifying a correlated entry in the PLCSdatabase to be associated with the input data item; searching the PLCSdatabase using said correlated entry; entering a received data elementfrom the input data item as a new data element of the PLCS database at alocation therein determined according to said search; retrieving one ormore data elements from the PLCS database according to said search;correlating said one or more retrieved data elements from the PLCSdatabase having the second database schema with a return data itemhaving heading data associated with a third database schema differentfrom the first and second database schemas; and outputting to a secondclient device the return data item which includes said heading dataassociated with the third database schema.
 18. The computer programproduct according to claim 17, wherein the process includes: receiving aplurality of client data elements within the received input data item.19. The computer program product according to claim 17, wherein theprocess includes one or more of: providing a first mapping databasecontaining a plurality of heading data items from a client databasehaving said first database schema and a plurality of data fields used inthe PLCS database, wherein each said heading data item is stored in thefirst mapping database in association with a respective said data field,and said correlating said heading data includes searching said firstmapping database to identify a said association; and/or providing asecond mapping database containing a plurality of heading data itemsfrom a client database having the third database schema and a pluralityof data fields used in the PLCS database, wherein each said data fieldis stored in the second mapping database in association with arespective said heading data item, and said correlating said one or moreretrieved data elements includes searching said second mapping databaseto identify a said association.
 20. The computer program productaccording to claim 17, wherein the process includes: receiving from thefirst client apparatus a first communication containing a firstidentifier identifying data for entry in the PLCS database; receivingfrom the second client apparatus a second communication containing asecond identifier different from the first identifier and identifyingdata for entry in, or retrieval from, the PLCS database; comparing thesecond identifier to the first identifier; and in response to thecomparison identifying a commonality between the second identifier andthe first identifier, determining that both the second identifier andthe first identifier correspond to a common data entry in the PLCSdatabase, mapping the second identifier and the first identifier to acommon identifier for the PLCS database, and accessing the PLCS databaseusing the common identifier according to the second communication.